Conversation
Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec.
Updated the API version from preview/2025-01-01-preview to preview/2025-04-01-preview.
Co-authored-by: SentinelEcoDevs <sentinelecodevs@microsoft.com>
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
|
Please can you fix all 'MISSING_APIS_IN_DEFAULT_TAG' errors in Avocado? |
| reason: This API is published to customers and we have not changed it in the past year, nor will we be able to change it without breaking changes to customers. | ||
| - code: DeleteResponseCodes | ||
| from: FileImports.json | ||
| reason: This API is published to customers and we have not changed it in the past year, nor will we be able to change it without breaking changes to customers. |
There was a problem hiding this comment.
I have a doubt, all these justifications about breaking changes not allowed - are they comparing to a previously released GA version, or only to a preview version?
There was a problem hiding this comment.
Hi @TimLovellSmith ,
We have alternative release between the GA release and the preview release. And some decide their preview release would not be merged to GA. So, when it is compared to previous GA release, we got those warnings. However, they are not related to the new changes in the current version. The same thing applied to the GA release as well.
There was a problem hiding this comment.
I approved the suppressions as it was already reviewed in the previous version
TimLovellSmith
left a comment
There was a problem hiding this comment.
Recording my general approval here. In general the change looks okay to me so far. Just have some 'wait and see feelings' around suppressions and keeping linter tools happy.
this was not yet fixed |
|
For 'MISSING_APIS_IN_DEFAULT_TAG', The error was caused by the switching parameter operationalInsightsResourceProvider to a fixed value Microsoft.OperationalInsights. Also some of the APIs are deprecated. For the operationalInsightsResourceProvider. Here is an example Definition of operationalInsightsResourceProvider Details of the error are in the following table.
|
|
/azp run |
|
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.